Esri File Geodatabase

The Esri File Geodatabse datastore is available for read and write 1Integrate as standard and with FME Desktop.

Read and Write Support

Read	Write		FME Desktop Required
Read	Commit	Copy To	FME Desktop Required

Data Support

Data	Support	Notes
Non-Spatial
2D
Measured
Heighted
3D		Note: Support for 3D is in BETA when using this data store. For more information about 3D data in 1Integrate, please refer to 3D Support.

Input and Output Parameters

Input Parameters

Parameter	Description
Source Files (.gdb)	Enter the location of the zip file containing the .gdb folder, or click Upload to navigate to the file on your network. Note: Ensure that the .gdb folder is at the root of the zip. If it isn't, the Geodatabase will not be read by 1Integrate.
Commit Destination Files (.gdb)	Results are available to download by clicking Download.
Coordinate Reference System	This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically. This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined). Note: Coordinate Reference System parameters are required in a session that will write data to Oracle. See Coordinate Reference System for more information on when this is required.
Allow invalid geometries	Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported. This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
Enable full 3D Geometries (BETA)	Select to enable full 3D geometries. Note: This parameter will only appear with an additional license enabling 3D support within 1Integrate. For more information on full 3D in 1Integrate, please see 3D Support.
For X, Y, Z, M data:	If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only. Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.
For coded field domains	Coded Field Domains declare a map of key value pairs (similar to a look-up). Use the following options to configure how 1Integrate handles these coded field Domains: Read the stored values, do not resolve: This is the default behaviour for 1Integrate. Values are read ignoring the coded field domain mappings. Read the resolved values: Convert the data read using the coded domains as a guide. This means that the value for the attribute will be replaced with any values retrieved from the coded field domains. Read both the stored and resolved values: A combination of the two options above. Creates new attributes postfixed with "`_RESOLVED`" for each required coded field domain mapping. The original attributes will contain the value read, and the newly created attributes will contain the value retrieved from the coded field domain.
Convert attribute names to upper case	If selected, attribute names will be converted to upper case.
Dissolve holes	If selected, dissolves adjacent holes in polygons.
Trim preceding spaces	If selected, preceding spaces in attribute values will be discarded.

Output Parameters

Parameter	Description
Destination Files (.gdb)	Results are available to download by clicking Download.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This can be used to specify the CRS of the output data if it cannot be deduced from the input data. This will not re-project the data, but allows it’s current CRS to be defined. See Coordinate Reference System for more information on when this is required.
Reverse coordinate axis order (y, x)	Reverse the x and y co-ordinate values.
Force geometry to be written with X, Y, Z, M	Select to output a fourth z or m ordinate for objects. Only takes effect if the geometry to be written has 3 ordinates.
For X, Y, Z, M data: Use zero rather than NULL or NaN when writing ignored ordinate	Select to write ignored values as zero in place of null/NaN (NaN is used for the PostGIS data store).

Copyright © 2022 1Spatial
1Integrate v 3.4
US Patent Number 9542416 B2 (2017-01-10)